Skip to content

[release-4.20] OCPBUGS-63010: E2E: Add test cases related to schedulable control plane nodes #1409

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Nov 8, 2025
Merged

[release-4.20] OCPBUGS-63010: E2E: Add test cases related to schedulable control plane nodes #1409

merged 1 commit into from
Nov 8, 2025

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Oct 14, 2025

This is an automated cherry-pick of #1405

/assign mrniranjan

@mrniranjan
E2E: Add test cases related to schedulable control plane nodes
d126ff7 
1. Adds test case to check of platform systemctl services are
restricted reserved cpus
2. Verify guaranteed pods cpus are removed from burstable pods
when created on schedulable control plane nodes

Signed-off-by: Niranjan M.R <mniranja@redhat.com>
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Oct 14, 2025
Merged
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 14, 2025

@openshift-cherrypick-robot: Jira Issue OCPBUGS-62839 has been cloned as Jira Issue OCPBUGS-63010. Will retitle bug to link to clone.
/retitle [release-4.20] OCPBUGS-63010: E2E: Add test cases related to schedulable control plane nodes

In response to this:

This is an automated cherry-pick of #1405

/assign mrniranjan

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from MarSik and jmencak October 14, 2025 00:21
@openshift-ci openshift-ci bot changed the title [release-4.20] OCPBUGS-62839: E2E: Add test cases related to schedulable control plane nodes [release-4.20] OCPBUGS-63010: E2E: Add test cases related to schedulable control plane nodes Oct 14, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Oct 14, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 14, 2025

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-63010, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.0) matches configured target version for branch (4.20.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-62839 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-62839 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
  • bug has dependents

Requesting review from QA contact:
/cc @mrniranjan

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #1405

/assign mrniranjan

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from mrniranjan October 14, 2025 00:21
@mrniranjan
Copy link
Contributor

mrniranjan commented Oct 28, 2025

/retest

@yanirq
Copy link
Contributor

yanirq commented Oct 28, 2025

/lgtm
/approve
/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Oct 28, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 28, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 28, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, yanirq

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 28, 2025
@mrniranjan
Copy link
Contributor

mrniranjan commented Nov 8, 2025

/verified by @mrniranjan

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 8, 2025

@mrniranjan: This PR has been marked as verified by @mrniranjan.

In response to this:

/verified by @mrniranjan

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 8, 2025
@mrniranjan
Copy link
Contributor

mrniranjan commented Nov 8, 2025

/retest

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 8, 2025

/retest-required

Remaining retests: 0 against base HEAD 56b12e2 and 2 for PR HEAD d126ff7 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 8, 2025

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-scos-e2e-aws-ovn d126ff7 link false /test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 2ed182b into openshift:release-4.20 Nov 8, 2025
18 of 19 checks passed
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 8, 2025

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-63010
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-63010 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

In response to this:

This is an automated cherry-pick of #1405

/assign mrniranjan

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jmencak jmencak Awaiting requested review from jmencak

@MarSik MarSik Awaiting requested review from MarSik

@mrniranjan mrniranjan Awaiting requested review from mrniranjan

Assignees

@mrniranjan mrniranjan

@yanirq yanirq

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@openshift-cherrypick-robot @openshift-ci-robot @mrniranjan @yanirq